Establish the Result of a Document Signature Process
Alias
SignerProcessResultUpdateDescription
Establishes the result of a document signature process.
Request
PUT /trustedx-resources/esignsp/v2/signer_processes/{signature_process_id}/resultParameters
|
Name |
Type |
Usage |
Description |
|
signature_process_id |
path |
Required |
Identifier of the document signature process whose result is to be established. |
Content-Type Header
Content-Type: application/jsonBody
The body of the request contains the following JSON object:
{ "status": {string}, "details": { "message": {string} }}|
Property |
Usage |
Description |
|
status |
Required |
Result assigned to the document signature process:
|
|
details.message |
Optional |
Additional information on the result of the document signature process. |
Authorization
The request must contain a bearer access token generated by an authorization server of the platform. This token must have a scope that includes the urn:safelayer:eidas:sign:process:document value and must be used as explained in RFC 6750. Basically, the access token must be included in an Authorization header as follows:
Authorization: Bearer <token>The access token must be obtained via a client credentials grant type OAuth 2.0 flow.
Response
Status-Line
If the result of the signature process is established successfully, the HTTP response will contain the following Status-Line (see HTTP Response Status for all the possible cases).
HTTP/1.1 200 OKContent-Type Header
Content-Type: application/jsonBody
If the result of the signature process is successfully established, the body of the response contains the JSON object included in the request
{ "status": {string}, "details": { "message": {string} }}